Method and apparatus for facilitating data management over a network

ABSTRACT

A method and apparatus for facilitating data management over a network are described. In one preferred embodiment, a request to display aggregate transaction data for a user is received, the aggregate transaction data containing data related to multiple disparate transactions organized into categories based on corresponding category codes and transaction codes associated with each transaction. The aggregate transaction data are retrieved from a database. A report containing the aggregate transaction data is generated and displayed for the user in a user interface area.

CROSS-REFERENCE TO RELATED APPLICATIONS

The application claims the benefit of U.S. Provisional Patent Application Ser. No. 60/598,330, filed on Aug. 2, 2004 and entitled “SPENDING MANAGEMENT SYSTEM AND METHOD,” which application is incorporated herein in its entirety by this reference thereto.

TECHNICAL FIELD

The invention relates generally to the field of network-based communications. More particularly, this invention relates to a method and apparatus for facilitating data management over a network, such as the Internet.

BACKGROUND OF THE INVENTION

The explosive growth of the Internet as a publication and interactive communication platform has created an electronic environment that is changing the way business is transacted. As the Internet becomes increasingly accessible around the world, online communications and business transactions increase exponentially.

Several attempts have been made to facilitate online management of financial data using such network-based communications, namely to provide software packages residing on a computer and configured, for example, to acquire data from network-based financial transaction facilities, and to facilitate organization and management of such data over the network. However, such packages do not provide a satisfactory level of data access and/or detail. For example, many of the current software applications rely on preparation and display of transaction lists, such as credit card monthly statements and/or bank account statements, but do not provide a system to organize such transactions. Other software applications allow categorization of transactions, but require user input and data downloading prior to such user-defined operations. Thus, what is needed is a method and apparatus that facilitate real-time data retrieval, organization, and management over a network, such as the Internet.

SUMMARY OF THE INVENTION

A method and apparatus for facilitating data management over a network are described. In one preferred embodiment, a request to display aggregate transaction data for a user is received, the aggregate transaction data containing data related to multiple disparate transactions organized into categories based on corresponding category codes and transaction codes associated with each transaction. The aggregate transaction data are retrieved from a database. A report containing the aggregate transaction data is generated and displayed for the user in a user interface area.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary network-based transaction and communications facility, which facilitates data management according an exemplary embodiment of the invention;

FIG. 2 is a block diagram illustrating a data management system within the network-based transaction and communications facility according to an exemplary embodiment of the invention;

FIG. 3 is a block diagram illustrating a management database, maintained by and accessed via a processing server within the data management system, which at least partially implements and supports the data management system according to an exemplary embodiment of the invention;

FIG. 4 is a flow diagram illustrating a method for aggregating data according to an exemplary embodiment of the invention;

FIG. 5 is a flow diagram illustrating a method for transmitting communications to users indicating availability of aggregate data according to an exemplary embodiment of the invention;

FIG. 6 is a flow diagram illustrating a method for facilitating data management according to an exemplary embodiment of the invention;

FIGS. 7A through 7D illustrate exemplary interfaces for facilitating data management according to an exemplary embodiment of the invention;

FIG. 8 is a flow diagram illustrating a method for facilitating display of detailed aggregate data according to an exemplary embodiment of the invention;

FIG. 9 is a flow diagram illustrating a method for facilitating customization of the aggregate data based on user input according to an exemplary embodiment of the invention; and

FIG. 10 is a diagrammatic representation of a machine in the exemplary form of a computer system within which a set of instructions may be executed.

DETAILED DESCRIPTION

FIG. 1 is a block diagram illustrating an exemplary network-based transaction and communications facility 10, such as, for example, a financial transaction facility, which facilitates transactions and communications with users and further facilitates data management according to the invention. While an exemplary embodiment of the invention is described within the context of a financial transaction and communications facility 10, it will be appreciated by those skilled in the art that the invention will find application in many different types of computer-based, and network-based, commerce facilities.

The facility 10 includes one or more of a number of types of front-end Web servers, namely, for example, pages servers 12, which deliver Web pages to multiple users, for example markup language documents, and processing servers 14, such as, for example, Common Gateway Interface (CGI) servers or Internet Server Application Program Interface (ISAPI) servers, which provide an intelligent interface to the back-end of the facility 10. In addition, the facility 10 may include communication servers 16 that provide, inter alia, automated communications, such as, for example, electronic mail (email) communications to/from users, and/or instant messaging (IM) functionality, to/from users of the facility 10.

The facility 10 further includes one or more back-end servers, for example, a credit card database server 22, a banking database server 24, each of which maintains and facilitates access to a respective database 23, 25 and a data management system, such as, for example, a financial management system 26, which will be described in further detail below.

The network-based facility 10 may be accessed by a client program 32, such as a browser, for example the Internet Explorer browser distributed by Microsoft Corporation of Redmond, Wash., which executes on a client machine 33 and accesses the facility 10 via a network 34, such as, for example, the Internet. Other examples of networks that a client may use to access the facility 10 include a wide area network (WAN), a local area network (LAN), a wireless network, e.g. a cellular network, or other known networks.

FIG. 2 is a block diagram illustrating a data management system within the network-based transaction and communications facility according to an exemplary embodiment of the invention. As illustrated in FIG. 2, in one preferred embodiment, the financial management system 26 includes one or more back-end management servers, of which management server 27 is shown, which maintain and facilitate access to a financial management database 28. The management server 27 and the database 28 at least partially implement and support the network-based facility 10 and are specifically provided to enable an exemplary embodiment of the present invention, as described in further detail below.

FIG. 3 is a block diagram illustrating a management database 28, maintained by and accessed via management server 27 within the data management system 26, according to an exemplary embodiment of the invention. The database 28 may, in one embodiment, be implemented as a relational database, and includes a number of tables having entries, or records, that are linked by indices and keys. In an alternative embodiment, the database 28 may be implemented as a collection of objects in an object-oriented database.

Central to the database 28 shown in FIG. 3 is a user table 40, which contains records for each entity or user of the facility 10. The database 28 also includes an accounts table 42, which may be linked to the user table 40 and may be populated with account information and data related to each user of the network-based facility 10.

The database 28 may include a number of other tables, which may also be shown to be linked to the user table 40, for example, tables specifically provided to enable an exemplary embodiment of the invention. One or more category tables 46 are configured to store multiple categories and respective category codes used to organize financial transactions associated with each user, as described in further detail below. In one embodiment, the stored categories include, for example, lodging, airlines, auto rental, restaurants, education, services, health care, gas/auto, retail, groceries, other travel/entertainment, other credit card transactions, ATM withdrawals, cash advances, checks written, electronic payments from checking account, transfers of funds, non-card withdrawals from the checking account, and other non-categorized online bill payment transactions. Alternatively, other categories related to financial transactions associated with a user may be stored in the category tables 46.

In one embodiment, user-generated access preferences, such as, for example a data access indicator, which indicates whether the user has access to data provided by the financial management system 26, and/or user-generated communication preferences, such as, for example, an email preference, which indicates whether the user has email notification privileges are stored in a user database within the transaction facility 10, such as, for example, in the banking database 25. All the above preferences are part of a user profile constructed and stored for each user. In an alternate embodiment, the user-generated access preferences and/or the user-generated communication preferences may be stored in one or more user preferences tables 44 within the financial management database 28. Prior to any communication between client 32 and the network-based facility 10, data related to financial transactions associated with each user are retrieved from respective databases maintained and accessed by the credit card database servers 22 and the banking database servers 24.

FIG. 4 is a flow diagram illustrating a method for aggregating data according to an exemplary embodiment of the invention. As illustrated in FIG. 4, at processing block 401, credit card transactions are retrieved for each user from the credit card database servers 22. In one embodiment, the management server 27 requests data related to credit card transactions associated with each user of the facility 10, the credit card transactions being stored in the database 23 associated with the credit card database servers 22. The credit card database servers 22 retrieve the credit card transactions and transmit the related data to the management server 27. Each credit card transaction datum includes, for example, a description of the transaction, the amount of the transaction, the location and date of the transaction, a predetermined credit card transaction code, and other data pertinent to the specific transaction. In an alternate embodiment, the retrieval of credit card transactions information may be performed in real-time during communications between the client 32 and the network-based facility 10.

At processing block 402, updated category codes are retrieved from the credit card database servers 22. In one embodiment, the management server 27 requests the updated category codes from the credit card database servers 22, such as, for example, merchant category codes defined by a merchant segmentation operation.

The credit card database servers 22 retrieve the updated category codes from the associated database 23 and transmit the retrieved category codes to the management server 27. In one embodiment, each retrieved category code corresponds to a category used in subsequent aggregation and management of data. In an alternate embodiment, the retrieval of updated category code information may be performed in real-time during communications between the client 32 and the network-based facility 10.

At processing block 403, banking transactions are retrieved for each user from the banking database servers 24. In one embodiment, the management server 27 requests data related to banking transactions associated with each user of the facility 10, the banking transactions being stored in the database 25 associated with the banking database servers 24. The banking database servers 24 retrieve the banking transactions and transmit the related data to the management server 27. In one embodiment, the retrieved banking transactions include, for example, debit account transactions, ATM transactions, check transactions, fund transfer transactions, non-card withdrawal transactions, and other transactions related to bank accounts owned by each user of the facility 10. In an alternate embodiment, the retrieved banking transactions include electronic bill payment transactions associated with each user and stored in the respective database 25. In another alternate embodiment, the retrieval of banking transactions information may be performed in real-time during communications between the client 32 and the network-based facility 10.

At processing block 404, transaction codes for the requested banking transactions are retrieved from the banking database servers 24. In one embodiment, the management server 27 requests the transaction codes associated with the banking transactions from the banking database servers 24. The banking database servers 24 retrieve the transaction codes and transmit the codes to the management server 27. In one embodiment, each banking transaction performed for a user account has an associated banking transaction code, which identifies the particular banking transaction. In an alternate embodiment, the retrieval of the transaction codes may be performed in real-time during communications between the client 32 and the network-based facility 10.

At processing block 405, the data related to the credit card transactions and the data related to the banking transactions are aggregated and organized into multiple categories using the retrieved category codes and transaction codes. In one embodiment, the management server 27 aggregates the retrieved data and organizes data based on the categories stored in the category tables 46.

At processing block 406, the aggregate transaction data are stored in the financial management database 28. In one embodiment, the management server 27 stores the aggregate transaction data into the account tables 44 within the database 28.

According to an exemplary embodiment of the invention, the retrieval and processing of data related to financial transactions of each user are performed prior to any communication between client 32 and the network-based facility 10. The management server 27 retrieves financial transaction information performed during a predetermined period of time, for example credit card transactions and banking transactions performed within the previous sixty days. Alternatively, the management server 27 may retrieve financial transaction information performed within any predetermined amount of time. In an alternate embodiment, subsequent to the initiation of communications between the client 32 and the network-based facility 10, the retrieval and precessing of data related to financial transactions of each user are performed in real-time, allowing each user to access the updated data in real-time.

According to an exemplary embodiment of the invention, electronic communications are exchanged between the facility 10 and the client 32 to indicate to each user the availability of the aggregate transaction data, as described in further detail below. FIG. 5 is a flow diagram illustrating a method for transmitting communications to users indicating availability of aggregate transaction data, according to an exemplary embodiment of the invention. As illustrated in FIG. 5, at processing block 501, user information including data access preferences and communication preferences for each user are retrieved from the database 25, or, in the alternative, from the management database 28. In one embodiment, the banking database servers 24 access the database 25 and retrieve user information, data access preferences and communication preferences associated with each user.

At processing block 502, users that have not opted out of communications indicating availability of aggregate transaction data and, thus, accept electronic notifications as a communication preference are selected. In one embodiment, the banking database servers 24 select only users that have not opted out of receipt of electronic notifications indicating the availability of aggregate transaction data.

At processing block 503, in one embodiment, the banking database servers 24 create a notification list containing the selected users. Finally, at processing block 504, periodic communications are transmitted to each selected user indicating the availability of aggregate transaction data. In one embodiment, the banking database servers 24 initiate an electronic communication with the client 32 via the communication servers 16 and transmit an email to each selected user indicating the availability of aggregate transaction data. Alternatively, the banking database servers 24 may initiate periodic communications with the client 32 via the communication servers 16 and transmit notifications related to the aggregate transaction data, such as, for example, periodic reminders of data updates or any other types of user notifications.

FIG. 6 is a flow diagram illustrating a method for facilitating data management according to an exemplary embodiment of the invention. As illustrated in FIG. 6, at processing block 601, a request to connect to the network-based transaction and communications facility 10 is received from a user. In one embodiment, the user initiates a communication with the facility 10 via the client 32 and the communication servers 16 and transmits a request to connect to the facility 10 through an authentication or login procedure.

At processing block 602, user information including data access preferences and communication preferences for each user are retrieved from the database 25 or, in the alternative, from the management database 28. In one embodiment, the banking database servers 24 access the database 25 and retrieve user information, data access preferences, and communication preferences associated with each user. Alternatively, the management server 27 accesses the database 28 and retrieves user information from the user table 40 and data access preferences and communication preferences associated with each user from the user preferences tables 44. The data access preferences indicate whether the user has access to data provided by the financial management system 26. If the user does not have access to data, the management server 27 transmits a message in a message window to the client 32 via the communication servers 16 and the network 34 and denies access to the data.

Otherwise, at processing block 603, eligible accounts associated with the user are retrieved from the databases 23, 25 associated with the credit card database servers 22 and the banking database servers 24, respectively. In one embodiment, subsequent to the receipt of the request to connect to the facility 10, the management server 27 communicates with the credit card database servers 22 and the banking database servers 24 and requests the financial accounts eligible for the data management operations. The respective servers 22 and 24 retrieve corresponding credit card accounts and banking accounts associated with the user and transmit the account information to the management server 27.

At processing block 604, a request to display aggregate transaction data in real-time is received from a user. In one embodiment, the user initiates a communication with the facility 10 via the client 32 and the communication servers 16 and transmits a request to display aggregate transaction data. The management server 27 receives the request from the communication servers 16 and proceeds to display the requested data, as described below.

At processing block 605, a decision is made whether the user has any accounts eligible for real-time data management operations. In one embodiment, the management server 27 makes a determination whether the user has any accounts eligible for data management operations by reviewing the retrieved accounts. If the user does not have any eligible accounts, at processing block 606, the management server 27 transmits a message in a message window to the client 32 via the communication servers 16 and the network 34 and denies access to the data.

Otherwise, if the user has eligible accounts, at processing block 607, aggregate transaction data associated with the eligible accounts of the user is retrieved. In one embodiment, the management server 27 accesses the management database 28 and retrieves the aggregate transaction data associated with the eligible accounts of the user from the account tables 42 within the database 28.

Finally, at processing block 608, a report containing the aggregate transaction data is generated and displayed for the user. In one embodiment, the management server 27 generates a report containing the aggregate transaction data and transmits the report to the client 32 via the communication servers 16, the pages servers 12, and the network 34. The report is displayed for the user in a report window within a user interface area. The user interface area presented to the user facilitates user interaction and communications with the network-based facility 10, as described in further detail below in connection with FIGS. 7A-7D, 8, and 9.

FIGS. 7A-7D illustrate exemplary interfaces for facilitating data management according to an exemplary embodiment of the invention. As illustrated in FIG. 7A, in one embodiment, the facility 10 displays a user interface area 610 in a window within the client machine 33 to facilitate communication of the request to display aggregate transaction information data for the user. The user interface area 610 includes a summary of accounts owned by the user, showing, for example, banking account numbers and balances, credit card account numbers and balances, loan account numbers and balances, and other financial information. The user interface area 610 further includes a link 611, which facilitates transmission of the request to the facility 10. The user selects the “View Spending Report” link 611 with a conventional mouse click command and the client machine 33 transmits the request to the management server 27 via the network 34 and the communication servers 16.

As illustrated in FIG. 7B, in one embodiment, the management server 27 displays the report in a user interface area 620. The user interface area 620 includes a report window 630, a number of command buttons, including, for example, a Customize Report button 632, and a number of window tabs, including a Spending Summary tab 633, a Credit Cards tab 634, a Check Cards tab 635, a Other Checking Activity tab 636, and a Bill Pay tab 637.

In one embodiment, if the Spending Summary tab 633 is activated with a conventional mouse click command, the report window 630 displays aggregate transaction data received from the management server 27. The aggregate transaction data are organized according to categories 640 stored in the category tables 46 within the management database 28. Each category 640 is an interactive link configured to facilitate further user interaction.

If the user activates one of the other tabs 634-637 with a conventional mouse click command, the report window 630 displays statements corresponding to respective credit card accounts, check card accounts, checking accounts, and/or bill pay accounts. As illustrated in FIG. 7D, if the user activates the Check Cards tab 635, for example, the report window 630 displays detailed individual check card transactions 650.

FIG. 8 is a flow diagram illustrating a method for facilitating display of detailed aggregate data according to an exemplary embodiment of the invention. As illustrated in FIG. 8, at processing block 701, a request to display detailed transaction data associated with a category is received. In one embodiment, referring also to FIG. 7B, the user selects an amount link 641 corresponding to a category 640 with a conventional mouse click command. Responsive to selection of the link 641, the client 32 transmits the request to display detailed transaction data associated with the category through the network 34 and the communication servers 16.

At processing block 702, the detailed transaction data for the requested category are retrieved from the management database 28. In one embodiment, the management server 27 receives the request from the client 32 and retrieves the detailed transaction data associated with the selected category from the account tables 42.

At processing block 703, a detailed report containing the detailed transaction data are generated and displayed for the user. In one embodiment, the management server 27 generates the detailed report containing the detailed transaction data and transmits the report to the client 32 via the communication servers 16, the pages servers 12, and the network 34. The detailed report is displayed for the user in a separate detailed report window (not shown) within the user interface area 620 shown in FIG. 7B.

FIG. 9 is a flow diagram illustrating a method for facilitating customization of the aggregate data based on user input according to an exemplary embodiment of the invention. As illustrated in FIG. 9, at processing block 801, a request to customize and display the report containing the aggregate transaction data is received. In one embodiment, referring also to FIG. 7B, the user selects the Customize Report link 632 with a conventional mouse click command. Responsive to selection of the link 632, the client 32 transmits the request to customize and display the report containing the aggregate transaction data through the network 34.

At processing block 802, the management server 27 facilitates selection of report options by the user. As illustrated in FIG. 7C, in one embodiment, subsequent to the receipt of the request to customize and display the report containing the aggregate transaction data, the management server 27 generates and displays an option window 660 in the user interface area 620. The option window 660 includes a number of customizing report options, such as, for example, a list of banking and/or credit card accounts 661, and facilitates selection by the user of one or more accounts that the user wants removed and/or added from the report containing the aggregate data.

Subsequent to selection of options with a conventional mouse click command, the client 32 transmits the selected options to the facility 10 via the network 34. At processing block 803, the management server 27 receives the selected report options transmitted by the client 32.

At processing block 804, selected aggregate transaction data are retrieved based on the report options. In one embodiment, the management server 27 applies the customizing report options to the current communication session with the client 32 and retrieves selected aggregate transaction data from the account tables 42 within the management database 28 based on the specific accounts selected by the user.

At processing block 805, a customized report containing the selected aggregate transaction data is generated and displayed for the user. In one embodiment, the management server 27 generates the customized report containing the selected data and transmits the report to the client 32 via the communication servers 16, the pages servers 12, and the network 34. The customized report is displayed for the user in a separate customized report window (not shown) within the user interface area 620 shown in FIG. 7B.

In an alternate embodiment, the option window 660 may include additional customizing report options to facilitate creation and display of various customized reports for the user. For example, the option window 660 may include a list of check card accounts, and/or other loan accounts associated with the user.

In another alternate embodiment, the option window 660 may facilitate user selection of an option to display detailed transactional information in its entirety over a significant period of time, such as, for example a rolling 13-month period of historical data. In yet another embodiment, the option window 660 may enable the user to compare a predetermined period of time from a current year with a similar period from a previous year, and produce profiles of financial expenditures, such as month-over-month, year-over-year, or year-to-date.

In another embodiment, the option window 660 may allow the user to save and retrieve report views, eliminating the need to recreate the report views during subsequent sessions. Users are given the option to save the customized report view as a default view, which then applies on a go-forward basis or until the user changes the selected report view. The management server 27 receives the saved customized report view and stores the report view as the default view in the management database 28.

In yet another embodiment, the option window 660 may enable the user to enter and save a budget amount for each predefined category 640 in order to track variances. The management server 27 receives the saved budget amounts and stores the budget amounts in connection with the respective categories 640 in the management database 28.

In yet another embodiment, the option window 660 may facilitate reclassification of individual transactions 650 to a different category 640, including past transactions stored in the database 28. The management server 27 may store the reclassified transactions in the database 28 and may also re-categorize the respective vendor/payee on a go-forward basis.

In yet another embodiment, the user interfaces 610 and 620, and the windows 630, 660, may include a link to other marketing or product-related sites of the facility 10 to facilitate user navigation to the respective sites.

In yet another embodiment, the option window 660 may enable the user to create custom categories 640 and to store the custom categories in the database 28 through the management server 27.

FIG. 10 shows a diagrammatic representation of a machine in the exemplary form of a computer system 900 within which a set of instructions, for causing the machine to perform any one of the methodologies discussed above, may be executed. In alternative embodiments, the machine may comprise a network router, a network switch, a network bridge, Personal Digital Assistant (PDA), a cellular telephone, a Web appliance or any machine capable of executing a sequence of instructions that specify actions to be taken by that machine.

The computer system 900 includes a processor 902, a main memory 904 and a static memory 906, which communicate with each other via a bus 908. The computer system 900 may further include a video display unit 910, e.g. a liquid crystal display (LCD) or a cathode ray tube (CRT). The computer system 900 also includes an alphanumeric input device 912, e.g, a keyboard, a cursor control device 914, e.g. a mouse, a disk drive unit 916, a signal generation device 918, e.g. a speaker, and a network interface device 920.

The disk drive unit 916 includes a machine-readable medium 924 on which is stored a set of instructions, i.e. software, 926 embodying any one, or all, of the methodologies described above. The software 926 is also shown to reside, completely or at least partially, within the main memory 904 and/or within the processor 902. The software 926 may further be transmitted or received via the network interface device 920.

It is to be understood that embodiments of this invention may be used as or to support software programs executed upon some form of processing core (such as the CPU of a computer) or otherwise implemented or realized upon or within a machine or computer readable medium. A machine readable medium includes any mechanism for storing or transmitting information in a form readable by a machine, e.g. a computer. For example, a machine readable medium includes read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals, e.g. carrier waves, infrared signals, digital signals, etc.; or any other type of media suitable for storing or transmitting information.

In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. 

1. A method for facilitating data management over a network, comprising the steps of: receiving a request to display aggregate transaction data for a user, said aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; retrieving said aggregate transaction data from a database; and generating a report containing said aggregate transaction data and displaying said report in a user interface area for said user.
 2. The method according to claim 1, further comprising the steps of: retrieving said each transaction from a plurality of disparate data sources; retrieving said category codes and said transaction codes associated with said each transaction; aggregating said plurality of disparate transactions into said plurality of categories using said category codes and said transaction codes to obtain said aggregate transaction data; and storing said aggregate transaction data in said database.
 3. The method according to claim 1, wherein said plurality of disparate transactions further comprises credit card transactions.
 4. The method according to claim 1, wherein said plurality of disparate transactions further comprises banking transactions.
 5. The method according to claim 3, wherein each credit card transaction of said credit card transactions further comprises any of a description of said transaction, an amount of said transaction, a location and date of said transaction, and a predetermined credit card transaction code.
 6. The method according to claim 4, wherein said banking transactions further comprise any of debit account transactions, ATM transactions, check transactions, fund transfer transactions, non-card withdrawal transactions, and electronic bill payment transactions.
 7. The method according to claim 2, wherein said step of retrieving said each transaction from said plurality of disparate data sources is performed in real-time during communications with said user.
 8. The method according to claim 2, wherein said step of retrieving said category codes and said transaction codes associated with said each transaction is performed in real-time during communications with said user.
 9. The method according to claim 1, further comprising the steps of: retrieving user information, data access preferences and communication preferences associated with said user; and determining whether said user is entitled to receive said aggregate transaction data based on said user information, said data access preferences, and said communication preferences.
 10. A method for facilitating data management over a network, comprising the steps of: facilitating selection of a link to request display of aggregate transaction data for a user, said aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; and facilitating real-time communication of a report generated to contain said aggregate transaction data and display of said report in a user interface area for said user.
 11. The method according to claim 10, further comprising the steps of: presenting a report window containing said report within said user interface area; and facilitating selection of a report link in said report window, said report link being configured to request display of detailed transaction data.
 12. The method according to claim 11, further comprising the steps of: responsive to said selection of said report link, presenting an option window in said user interface area, said option window further comprising a plurality of customizing report options to enable said display of said detailed transaction data; and facilitating selection of at least one customizing report option of said plurality of report options.
 13. The method according to claim 12, further comprising the steps of: responsive to said selection of said at least one customizing report option, generating a customized report; and facilitating display of said customized report for said user within a customized report window of said user interface area.
 14. A machine-readable medium containing executable instructions, which, when executed in a processing system, cause said processing system to perform a method for facilitating data management over a network, said method comprising the steps of: receiving a request to display aggregate transaction data for a user, said aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; retrieving said aggregate transaction data from a database; and generating a report containing said aggregate transaction data and displaying said report in a user interface area for said user.
 15. The machine-readable medium according to claim 14, wherein said method further comprises the steps of: retrieving said each transaction from a plurality of disparate data sources; retrieving said category codes and said transaction codes associated with said each transaction; aggregating said plurality of disparate transactions into said plurality of categories using said category codes and said transaction codes to obtain said aggregate transaction data; and storing said aggregate transaction data in said database.
 16. A machine-readable medium containing executable instructions, which, when executed in a processing system, cause said processing system to perform a method for facilitating data management over a network, said method comprising the steps of: facilitating selection of a link to request display of aggregate transaction data for a user, said aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; and facilitating real-time communication of a report generated to contain said aggregate transaction data and display of said report in a user interface area for said user.
 17. The machine-readable medium according to claim 16, wherein said method further comprises the steps of: presenting a report window containing said report within said user interface area; and facilitating selection of a report link in said report window, said report link being configured to request display of detailed transaction data.
 18. The machine-readable medium according to claim 17, wherein said method further comprises the steps of: responsive to said selection of said report link, presenting an option window in said user interface area, said option window further comprising a plurality of customizing report options to enable said display of said detailed transaction data; and facilitating selection of at least one customizing report option of said plurality of report options.
 19. The machine-readable medium according to claim 18, wherein said method further comprises the steps of: responsive to said selection of said at least one customizing report option, generating a customized report; and facilitating display of said customized report for said user within a customized report window of said user interface area.
 20. A system for facilitating data management over a network, comprising: means for receiving a request to display aggregate transaction data for a user, said aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; means for retrieving said aggregate transaction data from a database; and means for generating a report containing said aggregate transaction data and displaying said report in a user interface area for said user.
 21. A system for facilitating data management over a network, comprising: means for facilitating selection of a link to request display of aggregate transaction data for a user, said aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; and means for facilitating real-time communication of a report generated to contain said aggregate transaction data and display of said report in a user interface area for said user.
 22. A system for facilitating data management over a network, comprising: a database for storing aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; and at least one management server for receiving a request to display said aggregate transaction data for a user, for retrieving said aggregate transaction data from said database, and for generating a report containing said aggregate transaction data and displaying said report in a user interface area for said user.
 23. The system according to claim 22, wherein said at least one management server retrieves said each transaction from a plurality of disparate data sources, retrieves said category codes and said transaction codes associated with said each transaction, aggregates said plurality of disparate transactions into said plurality of categories using said category codes and said transaction codes to obtain said aggregate transaction data, and stores said aggregate transaction data in said database.
 24. The system according to claim 22, wherein said at least one management server retrieves user information, data access preferences and communication preferences associated with said user, and determines whether said user is entitled to receive said aggregate transaction data based on said user information, said data access preferences, and said communication preferences.
 25. A system for facilitating data management over a network, comprising: a database for storing aggregate transaction data containing data related to a plurality of disparate transactions organized into a plurality of categories based on category codes and transaction codes associated with each transaction of said plurality of disparate transactions; and at least one management server for facilitating selection of a link to request display of said aggregate transaction data for a user, and for facilitating real-time communication of a report generated to contain said aggregate transaction data and display of said report in a user interface area for said user.
 26. The system according to claim 25, wherein said at least one management server presents a report window containing said report within said user interface area, and facilitates selection of a report link in said report window, said report link being configured to request display of detailed transaction data.
 27. The system according to claim 26, wherein, responsive to said selection of said report link, said at least one management server presents an option window in said user interface area, said option window further comprising a plurality of customizing report options to enable said display of said detailed transaction data, and facilitates selection of at least one customizing report option of said plurality of report options.
 28. The system according to claim 27, wherein, responsive to said selection of said at least one customizing report option, said at least one management server generates a customized report, and facilitates display of said customized report for said user within a customized report window of said user interface area. 